Adaptive Graphics Subsystem Power and Performance Management

ABSTRACT

Examples are disclosed for adaptive graphics subsystem power and performance management including adjusting one or more power management or performance attributes for a graphics subsystem for a computing platform based on a comparison of a current quality metric to a target quality metric. The current and target quality metric to be separately determined based on current and target quality of service (QoS) values for power management and performance for at least portions of the computing platform.

BACKGROUND

Graphics subsystems that perform processing of images for computingplatforms may consume large amounts of power. Mobile computing platformsoperating under limited amounts of available power (e.g., battery power)typically deploy statically defined power management techniques forthese graphics subsystems. The statically defined power managementtechniques may be an attempt to balance power saving with computingplatform performance.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example computing platform.

FIG. 2 illustrates a block diagram of an example architecture for agraphics subsystem QoS manager.

FIG. 3 illustrates an example timing sequence.

FIG. 4 illustrates an example table for current power management QoSvalues.

FIG. 5 illustrates an example table for current performance QoS values.

FIG. 6 illustrates an example table for target power management QoSvalues.

FIG. 7 illustrates an example table for target performance QoS values.

FIG. 8 illustrates a flow chart of example operations for adaptivegraphics subsystem power and performance management.

FIG. 9 illustrates an example system.

FIG. 10 illustrates an example device.

DETAILED DESCRIPTION

As contemplated in the present disclosure, statically defined powermanagement techniques may be an attempt to balance power saving withcomputing platform performance. In some examples, these staticallydefined power management techniques may not be sensitive to applicationstates or modes of operation. Also, statically defined power managementtechniques may lack an ability to adapt to quality of service (QoS)constraints (e.g., from an application and/or user) to extend batterylife yet maintain acceptable performance.

Current statically defined power management techniques may transitionone or more graphics subsystems to lower power states if the one or moregraphics subsystems are idle for a fixed period of time. The transitionto the lower power states may occur without considering the platform'scurrent mode of operation, application workload/requirements, user QoSrequirements, etc. The fixed period of time without knowledge of thenext wakeup from active to a lower power state may lead to frequenttransitions between low power states (e.g., sleep states) to higherpower states (e.g., active states). The frequent transitions may lead todips in performance due to associated context save-and-restores andpower loss due to transitional overhead. Also, statically defined powermanagement techniques are likely not flexible enough to adapt toaggressive, device specific power and performance management, anduser/application QoS constraints.

In some examples, techniques are implemented for adaptive graphicssubsystem power and performance management. For these examples, acurrent power management quality of service (QoS) value and a currentperformance QoS value may be received. The current power management andperformance QoS values may be associated with a first mode of operation.A current quality metric may then be determined based, at least in part,on the current power management and performance QoS values. A targetpower management QoS value and a target performance QoS value may alsobe received. The target power management and performance QoS values maybe associated with a second mode of operation. A target quality metricmay also be determined based, at least in part, on the target powermanagement and performance QoS values. One or more power management orperformance attributes for one or more graphics subsystems of acomputing platform may be adjusted based, at least in part, on acomparison of the current quality metric to the target quality metric.For example, an idle time-out window may be adjusted. The idle time-outwindow, for example may include a time interval for which the one ormore graphics subsystems remain in an active state following executionof a command before transitioning into a low power state.

FIG. 1 illustrates an example computing platform 100. As shown in FIG.1, computing platform 100 includes an operating system 110, applications130-1 to 130-n, a platform power management 140, a memory 150,communications (comms) 160, a central processing unit (CPU) 170, asecurity engine 180 and secure storage 190. Also, as shown in FIG. 1,computing platform 100 includes a display controller 120-1, a camera120-2, 2-dimensional/3-dimensional (2D/3D) graphics 120-3, a videoencode 120-4 and a video decode 120-5. In some examples, displaycontroller 120-1, camera 120-2, 2D/3D graphics 120-3, video encode 120-4and video decode 120-5 may be either separately or jointly identified asa graphics subsystem for computing platform 100. Although thisdisclosure not limited to graphics subsystems including the fivegraphics subsystems shown in FIG. 1.

According to some examples, several interfaces are also depicted in FIG.1 for interconnecting and/or communicatively coupling elements ofcomputing platform 100. For example, QoS user interface 115 andinterface 125 may allow for users (not shown) and/or applications 130-1to 130-n to couple to operating system 110. Also, interface 135 mayallow for platform power management 140 or elements of operating system110 to communicatively couple to elements of computing platform 100 suchas CPU 170, memory 150 or one or more of the graphic subsystemsmentioned above. Interface 154, for example, may allow hardware and/orfirmware elements of computing platform 100 to communicatively coupletogether, e.g., via a system bus or other type of internal communicationchannel.

In some examples, as shown in FIG. 1, operating system 110 may includedevice driver(s) 112 and graphics subsystem QoS manager 114. Devicedriver(s) 112 and graphics subsystem QoS manager 114 may include logicand/or features configured to interact with other elements of computingplatform 100 (e.g., via interface 135). Also, as shown in FIG. 1,graphics subsystem QoS manager 114 may also interact with devicedriver(s) 112 or platform power management 140.

According to some examples, device driver(s) 112 may include one or moregraphics subsystem drivers to interact with display controller 120-1,camera 120-2, 2D/3D graphics 120-3, video encode 120-4 or video decode120-5. For these examples, device driver(s) 112 may provide currentperformance QoS values associated with one or more of these graphicssubsystems to graphics subsystem QoS manager 114. As described morebelow, the current performance QoS values may be compared to targetperformance QoS values and then may be used to adjust one or more powermanagement or performance attributes for the one or more graphicssubsystems.

In some examples, platform power management 140 may include logic and/orfeatures to gather system power information for computing platform 100.For example, platform power management 140 may gather system stateinformation for computing platform 100 such as whether CPU 170 is anactive or sleep power state or whether a battery (not shown) hasadequate power. Platform power management 140, for example, may providecurrent power management values associated with this gathered systemstate information to graphics subsystem QoS manager 114. As describedmore below, a current quality metric (QM) determined from the currentpower management QoS values may be compared to a target QM determinedfrom the target power management QoS values. One or more powermanagement or performance attributes for the one or more graphicssubsystems may then be adjusted based on the comparison.

Although not shown in FIG. 1, in some examples, graphics subsystem QoSmanager 114 may be included with the logic and/or features of devicedriver(s) 112. For these examples, the graphics subsystem QoS manager114 within device driver(s) 112 may interact with platform powermanagement 140 to obtain current power management QoS values. Also,graphics subsystem QoS manager 114 may cooperate with device driver(s)112 to obtain current performance QoS values from the one or moregraphics subsystems of computing platform 100.

According to some examples, as shown in FIG. 1, platform powermanagement 140 may be implemented as logic and/or features configured toeither independently manage power or cooperate with operating system 110to manage power for computing platform 100. In other examples, althoughnot shown in FIG. 1, platform power management 160 may be included as asoftware module operating within operating system 110.

According to some examples, memory 150 may be implemented as a volatilememory device utilized by various elements of computing platform 100(e.g., as off-chip memory). For these implementations, memory 130 mayinclude, but is not limited to, random access memory (RAM), dynamicrandom access memory (DRAM) or static RAM (SRAM).

In some examples, comms 160 may include logic and/or features to enablecomputing platform 100 to communicate externally with elements remote tocomputing platform 100. These logic and/or features may includecommunicating over wired and/or wireless communication channels via oneor more wired or wireless networks. In communicating across suchnetworks, comms 160 may operate in accordance with one or moreapplicable communication or networking standards in any version.

According to some examples, CPU 170 may be implemented as a centralprocessing unit for computing platform 100. CPU 170 may include one ormore processing units having one or more processor cores or having anynumber of processors having any number of processor cores. CPU 170 mayinclude any type of processing unit, such as, for example, amulti-processing unit, a reduced instruction set computer (RISC), aprocessor having a pipeline, a complex instruction set computer (CISC),digital signal processor (DSP), and so forth.

In some examples, security engine 180 may enable or facilitate secureoperations on computing platform 100. In some examples, security engine180 may manage or control access to secure storage 190. Secure storage190, for example, may include encrypted information that may only bedecrypted by logic and/or features of security engine 180.

As mentioned above, interface 154, may allow hardware and/or firmwareelements of computing platform 100 to communicatively couple together.According to some examples, communication channels interface 154 mayoperate in accordance with one or more protocols or standards. Theseprotocols or standards may be described in one or one or more industrystandards (including progenies and variants) such as those associatedwith the Inter-Integrated Circuit (I²C) specification, the SystemManagement Bus (SMBus) specification, the Accelerated Graphics Port(AGP) specification, the Peripheral Component Interconnect Express (PCIExpress) specification, the Universal Serial Bus (USB), specification orthe Serial Advanced Technology Attachment (SATA) specification. Althoughthis disclosure is not limited to only the above-mentioned standards andassociated protocols.

In some examples, computing platform 100 may be at least part of amobile computing device. Examples of a mobile computing device mayinclude a personal computer (PC), laptop computer, ultra-mobilecomputer, tablet, touch pad, portable computer, handheld computer,palmtop computer, personal digital assistant (PDA), cellular telephone,combination cellular telephone/PDA, television, smart device (e.g.,smart phone, smart tablet or smart television), mobile internet device(MID), messaging device, data communication device, and so forth

FIG. 2 illustrates a block diagram of an example architecture forgraphics subsystem QoS manager 114. As described above for computingplatform 100 in FIG. 1, operating system 110 may include graphicssubsystem QoS manager 114. In some examples, graphics subsystem QoSmanager 114 includes features and/or logic configured or arranged toprovide adaptive graphics subsystem power and performance management.

The example graphics subsystem QoS manager 114 of FIG. 2, includes QoSlogic 210, control logic 220, a memory 230 and input/output (110)interfaces 240. As illustrated in FIG. 2, QoS logic 210 may be coupledto control logic 220, memory 230 and I/O interfaces 240. QoS logic 210may include one or more of a mode feature 211, a receive feature 213, acurrent feature 215, a target feature 217, or an adjust feature 219, orany reasonable combination thereof.

In some examples, the elements portrayed in FIG. 2 are configured tosupport or enable graphics subsystem QoS manager 114 as described inthis disclosure. A given graphics subsystem QoS manager 114 may includesome, all or more elements than those depicted in FIG. 2. For example,QoS logic 210 and control logic 220 may separately or collectivelyrepresent a wide variety of logic device(s) or executable content toimplement the features of graphics subsystem QoS manager 114. Examplelogic devices may include one or more of a microprocessor, amicrocontroller, a process circuit, a field programmable gate array(FPGA), an application specific integrated circuit (ASIC), a sequesteredthread or a core of a multi-core/multi-threaded microprocessor or acombination thereof.

In some examples, as shown in FIG. 2, QoS logic 210 includes modefeature 211, receive feature 213, current feature 215, target feature217, or adjust feature 219. QoS logic 210 may be configured to use oneor more of these features to perform operations. For example, modefeature 211 may determine whether a change in mode has occurred, e.g.,responsive to a change in type of usage for one or more graphicsubsystems of computing platform 100. Receive feature 213 may thenreceive current and target power management and performance QoS valuesassociated with different modes of operation. Current feature 215, asdescribed more below, may determine a current quality metric (QM) basedon the received current power management and performance QoS values.Target feature 217, also as described more below, may determine a targetQM based on the received target power management and performance QoSvalues. Adjust feature 219 may then adjust one or more power managementor performance attributes for the one or graphic subsystems based on acomparison of the current QM to the target QM.

In some examples, control logic 220 may be configured to control theoverall operation of graphics subsystem QoS manager 114. As mentionedabove, control logic 220 may represent any of a wide variety of logicdevice(s) or executable content. For some examples, control logic 220may be configured to operate in conjunction with executable content orinstructions to implement the control of graphics subsystem QoS manager114. In some alternate examples, the features and functionality ofcontrol logic 220 may be implemented within QoS logic 210.

According to some examples, memory 230 may be arranged to storeexecutable content or instructions for use by control logic 220 and/orQoS logic 210. The executable content or instructions may be used toimplement or activate features or elements of graphics subsystem QoSmanager 114. As described more below, memory 230 may also be arranged toat least temporarily maintain information associated with determiningcurrent and target QMs and adjusting one or more power management orperformance attributes for one or more graphics subsystems based on acomparison of the current QM to the target QM.

Memory 230 may include a wide variety of memory media including, but notlimited to, one or more of volatile memory, non-volatile memory, flashmemory, programmable variables or states, RAM, ROM, or other static ordynamic storage media.

In some examples, I/O interfaces 240 may provide an interface via alocal communication medium or link between graphics subsystem QoSmanager 114 and elements of computing platform 100 depicted in FIG. 1.I/O interfaces 240 may include interfaces that operate according tovarious communication protocols to communicate over the localcommunication medium or link (e.g., I²C, SMBus, AGP, PCI Express, USB,SATA, etc).

FIG. 3 illustrates an example timing sequence 300. In some examples,graphics subsystem QoS manager 114 as shown in FIG. 1 or described inFIG. 2 may include logic and/or features to cause adjustments totime-out windows 312, 322, 332 and 342 during timing sequence 300. Forthese examples, modes 310, 320, 330 and 340 may represent changes inmodes of operation for computing platform 100 and/or the graphicsubsystems of computing platform 100 during timing sequence 300. Thesechanges in modes of operations may be responsive to a change in a typeof usage of the one or more graphics subsystem, an application request(e.g., from application 130-1), a user request, an expiration of a timeinterval or an initialization of computing platform 100. It may beappreciated that embodiments are not limited to only these five examplesof what may trigger a change in a mode of operation, any number oftriggers may trigger a change of mode for a given implementation.

According to some examples, as shown in FIG. 3, mode 310 may be inresponse to an initialization. For these examples, computing platform100 may have been powered down and the powered down state may representa first mode of operation for computing platform 100. Mode 310, forthese examples, may therefore represent a second mode of operation.Also, modes 320, 330 and 340 may represent subsequent modes ofoperation.

In some examples, graphics subsystem QoS manager 114 may include logicand/or features to receive or obtain current power management andperformance QoS values associated with the first mode of operation,which as mentioned above, was a powered down state for computingplatform 100. For these examples, the current power management andperformance QoS values associated with the first mode may be based ondefault power management and performance QoS values. Also, for thesecond mode, graphics subsystem QoS manager 114 may include logic and/orfeatures to receive or obtain target power management and performanceQoS values that may be based a type of usage of the one or more graphicssubsystems of computing platform 100. These types of usage may include,but are not limited to, support for web browsing, video playback,interactive gaming or image capture.

According to some examples, graphics subsystem QoS manager 114 mayinclude logic and/or features to determine current and target QMs basedon the current and target QoS values obtained in response to mode 320.Graphics subsystem QoS manager 114 may then adjust one or more powermanagement and performance attributes for one or more graphicssubsystems of computing platform 100 based on a comparison of thecurrent and target QMs. These one or more power management andperformance attributes may include an idle time-out interval for whichthe one or more graphics subsystems remain in an active state followingexecution of a command (e.g., to support a type of usage) beforetransitioning into a low power state.

In some examples, the one or more power management and performanceattributes associated with the current/default power management andperformance QoS values may indicate an idle time-out window of 50milliseconds (ms). The type of usage at mode 320, for example, may beweb browsing. An idle time-out window of 50 ms may be an acceptablepower management and performance attribute for this type of usagebecause a relatively long period of time may pass between active andidle states. Graphics subsystem QoS manager 114 may maintain the idletime-out window at 50 ms as shown for time-out window 312 in FIG. 3.

According to some examples, at mode 320 the type of usage may change tographics intensive use such as an interactive game. Graphics subsystemQoS manager 114 may obtain a new set of current and target powermanagement and performance QoS values. The newly obtained target powermanagement and performance QoS values may indicate an idle time-outwindow of 100 ms. The longer idle time-out may be due to a graphicsintensive use of the interactive game that may cause the graphicssubsystems of computing platform to execute bursts of commands withrelatively short idle times between the bursts. For these examples,graphics subsystem QoS manager 114 may adjust the idle time-out windowas shown for time-out window 322 in FIG. 3. The longer idle time-outwindow 322 may keep the graphic subsystems in an active state betweenbursts of commands rather than powering up and down between bursts.

In some examples, at mode 330 the type of usage may change back to webbrowsing. Graphics subsystem QoS manager 114 may obtain another new setof current and target power management and performance QoS values. Asmentioned above, an idle time-out window of 50 ms may be an acceptablepower and performance attribute for this type of usage. Graphicssubsystem QoS manager 114 may adjust the idle time-out window back to 50ms as shown for time-out window 332 in FIG. 3.

According to some examples, at mode 340 the type of usage may change yetagain to another type of usage such as image capture. Graphics subsystemQoS manager 114 may obtain yet another new set of current and targetpower management and performance QoS values. The newly obtained targetpower management and performance QoS values may indicate an idletime-out window of 25 ms. The shorter idle time-out may be due to a lessgraphics intensive use associated with an image capture usage. The imagecapture usage may cause the graphics subsystems of computing platform toexecute short bursts of commands followed by relatively long periodsbetween the next burst of commands. Thus, for example, a relativelyshort idle time of around 25 ms may be an acceptable power managementand performance attribute for this type of usage.

In some examples, time-out windows 312, 322, 332 and 342 may also beshortened or lengthened due to power management constraints or based ona collected or compiled history of graphics subsystem activity ofcomputing platform 100. For example, a low battery for computingplatform 100 during extended periods of sustained activity may lead to ashorter idle time-out window in order to conserve power. Also, a historyof usage may indicate that an idle time-out window of relatively longduration at initialization of computing platform 100 (e.g., at mode 310)may be warranted. The longer idle time-out window at initialization maybe due to a user or applications historically requiring more or greateruse of graphics subsystems during initialization or powering up ofcomputing platform 100.

FIG. 4 illustrates an example table 400 for current power management QoSvalues. In some examples, graphics subsystem QoS manager 114 may includelogic and/or features to receive current power management QoS values(e.g., from device driver(s) 112). Graphics subsystem QoS manager 114may then populate or build table 400 (e.g., via current feature 215)based on the received current power management QoS values.

As shown in FIG. 4, table 400 includes separate and averaged power vs.performance ratings for various power management attributes includingthe general power management attributes of display, graphics & video,and system power. Current power management QoS values of “3” may be anindication that power management is more highly rated than performance.Current power management QoS values of values of “2” may indicate equalrating. Current power management QoS values of values of “1” mayindicate that power management is rated less compared to performance.

In some examples, current power management QoS values may be the resultof various settings or operating parameters for the graphics subsystemsof computing platform 100. The various setting, for example, may beassociated with a type of usage for these graphics subsystems. The typeof usage may include, but is not limited to, a default usage (e.g.,established at initialization at possibly set by a device manufacturer),a web browsing usage, a video playback usage, interactive game usage oran image capture usage. The various settings may also be associated withsystem power capabilities such as an amount of battery power availableto meet power management needs or objectives.

According to some examples, as shown in FIG. 4, the display powermanagement attribute may include resolution, brightness, refresh rate,and depth. The display power management attributes, for example, may beassociated with power management attributes for the graphics subsystemof display controller 120-1. Resolution, brightness, refresh rate anddepth, for example, may also be associated with attributes for a displaycontrolled by display controller 120-1. Resolution, for example, mayinclude pixel resolution. Brightness may include display brightness.Refresh rate may include display refresh rates and depth may includepixel depths or pixel memory sizes (e.g., 24-bit, 32-bit, etc.).

In some examples, as shown in FIG. 4, the graphics & video powermanagement attribute may include texture, render target, overlay type,frequency, copy rate, mipmap, and compression ratio. The graphics &video power management attribute may be associated with power managementattributes for the graphics subsystems of camera 120-2, 2D/3D graphics120-3, video encode 120-4 or video decode 120-5. Texture, for example,may include compressed texture formats. Render target may include softrendering or full rendering. Overlay type may include either overlay ortexture based video. Frequency may include the frequency for one or moregraphics subsystems (e.g., 2D/3D graphics 120-3) to execute commands.Copy rate may include a copy rate (e.g., blits) from a source buffer toa destination buffer. Mipmap may include an indication of 3D imagerendering and compression ratio may include the compression ratio viawhich video may be encoded or decoded by one or more graphics subsystems(e.g., video encode 120-4 and/or video decode 120-5).

In some examples, as shown in FIG. 4, the system power attribute mayinclude system state and battery power. The system power attributes maybe associated with power management attributes that may impact all orportions of the graphics subsystems of computing platform 100. Systemstate may include the current power state of computing platform 100(e.g., active, idle, sleep, etc.). Battery power may include the systembattery power available to power the graphics subsystems.

In some examples, the current power management QoS values shown in table400 of FIG. 4 may be associated with the current mode of operation forcomputing platform 100. Graphics subsystem QoS manager 114 may includelogic and/or features to determine a current power management average(PM_(ave)) based on average current power management QoS values fordisplay, graphics and video, and system power. For example, currentPM_(ave) derived from the values shown in table 400 may be (2.5, 2,1.5). The current PM_(ave) (2.5, 2, 1.5) may indicate a relatively highrating for display attributes (2.5), a medium rating for graphics andvideo (2) and a relatively low rating on system attributes (1.5).

FIG. 5 illustrates an example table 500 for current performance QoSvalues. In some examples, graphics subsystem QoS manager 114 may includelogic and/or features to receive current performance management QoSvalues (e.g., from platform power management 140). Graphics subsystemQoS manager 114 may then populate or build table 500 (e.g., via currentfeature 215) based on the received current performance management QoSvalues.

As shown in FIG. 5, table 500 includes separate and averaged performancevs. power ratings for various performance attributes including thegeneral performance attributes of display, graphics & video,application, user experience and system performance. Current performancemanagement QoS values of “3” may be an indication that performance ismore highly rated than power management. Current performance managementQoS values of “2” may indicate equal rating. Current performancemanagement QoS values of “1” may indicate that performance management israted less compared to power management.

In some examples, similar to current power management QoS values,current performance management QoS values may be the result of varioussettings or operating parameters for the graphics subsystems ofcomputing platform 100. The various setting, for example, may also beassociated with a type of usage for these graphics subsystems. Thevarious settings may also be associated with system performancecapabilities or constraints such as available processing power at CPU170 or available processing power at one or more of the graphicssubsystems.

According to some examples, as shown in FIG. 5, the display performanceattribute may include resolution, brightness, refresh rate, and depth.The display performance attributes may be associated with powermanagement attributes for the graphics subsystem of display controller120-1. Resolution, brightness, refresh rate and depth, for example, maybe associated with attributes for a display controlled by displaycontroller 120-1. Resolution, for example, may include pixel resolution.Brightness may include display brightness. Refresh rate may includedisplay refresh rates and depth may include pixel depths or pixel memorysizes.

In some examples, as shown in FIG. 5, the graphics & video performanceattribute may include texture, render target, overlay type, frequency,copy rate, mipmap, and compression ratio. The graphics & videoperformance attribute may be associated with performance attributes forthe graphics subsystems of camera 120-2, 2D/3D graphics 120-3, videoencode 120-4 or video decode 120-5. Texture, for example, may includecompressed texture formats. Render target may include soft rendering orfull rendering. Overlay type may include either overlay or texture basedvideo. Frequency may include the frequency for one or more graphicssubsystems to execute commands. Copy rate may include a copy rate (e.g.,blits) from a source buffer to a destination buffer. Mipmap may includean indication of 3D image rendering and compression ratio may includethe compression ratio via which video may be encoded or decoded by oneor more graphics subsystems of computing platform 100.

In some examples, as shown in FIG. 5, the application performanceattribute may include maximum latency. Maximum latency, for example, mayinclude a maximum time interval via which an application can toleratewhen using one or more graphics subsystems of computing platform 100.For example, an application associated with video playback may set amaximum latency for decoding video using video decode 120-5. The maximumlatency, for example, may ensure that video frames are decoded at a rateto ensure that corresponding audio frames match the video frames. A timeinterval of a relatively short time period may result in a high ratingfor performance and a relatively long time period may result in a lowrating.

According to some examples, as shown in FIG. 5, the user experienceattribute may include maximum response. Maximum response, for example,may include a maximum time interval via which a user can tolerate whenusing one or more graphics subsystems of computing platform 100. Forexample, a user playing an interactive game may set a maximum responsefor the rendering of 2D/3D graphics by 2D/3D graphics 120-3 in order toincrease the user experience of the interactive game. A time interval ofa relatively short time period may result in a high rating forperformance vs. power management and a relatively long time period mayresult in a low rating for performance vs. power management.

In some examples, as shown in FIG. 5, the system performance attributemay include system state. The system performance attributes may beassociated with performance attributes that may impact all or portionsof the graphics subsystems of computing platform 100. System state, forexample, may include the current power state of computing platform 100(e.g., active, idle, sleep, etc.).

In some examples, the current performance QoS values shown in table 500of FIG. 5 may be associated with the current mode of operation forcomputing platform 100. Graphics subsystem QoS manager 114 may includelogic and/or features to determine a current performance average(PF_(ave)) based on average current performance QoS values for display,graphics and video, application, user experience, and systemperformance. For example, the current PF_(ave) derived from the valuesshown in table 500 may be (2, 3, 2, 3, 3). The current PF_(ave) (2, 3,2, 3, 3) may indicate high ratings for the graphics and video, userexperience, and system performance attributes and a medium rating forthe display and application attributes.

According to some examples, graphics subsystem QoS manager 114 mayinclude logic and/or features to determine a current QM. The current QMmay be a combination of current PM_(ave) (2.5, 2, 1.5) and currentPF_(ave) (2, 3, 2, 3, 3). One example of combining current PM_(ave)(2.5, 2, 1.5) and current PF_(ave) (2, 3, 2, 3, 3) may include takingthe values of 2.5, 2, and 1.5 included in current PM_(ave) (2.5, 2, 1.5)and averaging these values to arrive at an overall current PM_(ave) (2).Also, the averages of 2, 3, 2, 3 and 3 included in current PF_(ave) maybe averaged to arrive at overall current PF_(ave) (2.6). Overall currentPM_(ave) (2) and overall current PF_(ave) (2.6) may then be combined toarrive at current QM (2, 2.6). As mentioned below, the current QM (2,2.6) may be compared to a target QM and then graphics subsystem QoSmanager 114 may make adjustments to one or more power management orperformance attributes based on the comparison.

FIG. 6 illustrates an example table 600 for target power management QoSvalues. In some examples, graphics subsystem QoS manager 114 may includelogic and/or features to receive target power management QoS values(e.g., from device driver(s) 112, applications 130-1 to 130-n or users).Graphics subsystem QoS manager 114 may then populate or build table 600(e.g., via target feature 217) based on the received target powermanagement QoS values.

According to some examples, as shown in FIG. 6, table 600 is similar totable 400 depicted in FIG. 4. As such, table 600 includes the same powermanagement attributes as table 400. However, the ratings for the variouspower management attributes are target ratings rather than currentratings.

In some examples, target power management QoS values may be the resultof various targeted settings or operating parameters for the graphicssubsystems of computing platform 100. The various targeted setting, forexample, may be associated with a proposed type of usage for thesegraphics subsystems. The proposed type of usage may include, but is notlimited to, a web browsing usage, a video playback usage, interactivegame usage or an image capture usage. The various setting may also beassociated with system power capabilities such as an amount of batterypower available to meet power management needs or objectives forplatform 100's anticipated operating power state(s).

According to some examples, the target power management QoS values shownin table 600 of FIG. 6 may be associated with a target mode of operationfor computing platform 100. Graphics subsystem QoS manager 114 mayinclude logic and/or features to determine a target PM_(ave) based onaverage target power management QoS values for display, graphics andvideo, and system power. For example, the target PM_(ave) derived fromvalues shown in table 6 may be (1, 1, 1). The target PM_(ave) (1, 1, 1)may indicate a low rating on all target power management attributes.

FIG. 7 illustrates an example table 700 for target performance QoSvalues. In some examples, graphics subsystem QoS manager 114 may includelogic and/or features to receive target performance management QoSvalues (e.g., from device driver(s) 112, applications 130-1 to 130-n orusers). Graphics subsystem QoS manager 114 may then populate or buildtable 700 (e.g., via target feature 217) based on the received targetperformance management QoS values.

According to some examples, as shown in FIG. 7, table 700 is similar totable 500 depicted in FIG. 5. As such, table 700 includes the sameperformance attributes as table 500. However, the ratings for thevarious performance attributes are target ratings rather than currentratings.

In some examples, target performance QoS values may be the result ofvarious targeted settings or operating parameters for the graphicssubsystems of computing platform 100. The various targeted setting, forexample, may be associated with a proposed type of usage for thesegraphics subsystems. The proposed type of usage may include, but is notlimited to, a web browsing usage, a video playback usage, interactivegame usage or an image capture usage. The various setting may also beassociated with application requirements (e.g., maximum latency), userexperience requirements (maximum response) or system performancecapabilities such as available processing power or proposed operatingstates.

According to some examples, the target performance QoS values shown intable 700 of FIG. 7 may be associated with a target mode of operationfor computing platform 100. Graphics subsystem QoS manager 114 mayinclude logic and/or features to determine a target PF_(ave) based onaverage target performance QoS values for display, graphics and video,application, user experience and system performance. For example, thetarget PF_(ave) derived from the values shown in table 700 may be (3, 3,3, 3, 3). The target PF_(ave) (3, 3, 3, 3, 3) may indicate a high ratingon all target performance attributes.

In some examples, graphics subsystem QoS manager 114 may include logicand/or features to determine a target QM. The target QM may be acombination of target PM_(ave) (1, 1, 1) and target PF_(ave) (3, 3, 3,3, 3). One example of combining target PM_(ave) (1, 1, 1) and targetPF_(ave) (3, 3, 3, 3, 3) may include taking the values of 1, 1 and 1included in target PM_(ave) (1, 1, 1) and averaging these values toarrive at an overall target PM_(ave) (1). Also, the averages of 3, 3, 3,3 and 3 included in target PF_(ave) may be averaged to arrive at overalltarget PF_(ave) (3). Overall target PM_(ave) (1) and overall targetPF_(ave) (3) may then be combined to arrive at target QM (1, 3).

According to some examples, graphics subsystem QoS manager 114 mayinclude logic and/or features to compare target QM (1, 3) to current QM(2, 2.6) and may make adjustments to one or more power management orperformance attributes based on the comparison (e.g., via adjust feature219). For example, graphics subsystem QoS manager 114 may attempt toadjust the one or more power management or performance attributes shownin tables 400 and 500 such that the averages of the average ratings forthe power management and performance attributes will change current QM(2, 2.6) to match target QM (1, 3). As a result, the current QM (2, 2.6)becomes adjusted current QM (1, 3). The adjusted current QM (1, 3) nowindicates that computing platform places a low overall rating on powermanagement and a high overall rating on performance. Also, adjustedcurrent power management and performance QoS values will reflect thischange in rating.

FIG. 8 illustrates a flow chart of example operations for adaptivegraphics subsystem power and performance management. In some examples,elements of computing platform 100 as shown in FIG. 1 may be used toillustrate example operations related to the flow chart depicted in FIG.8. Graphics subsystem QoS manager 114 as shown in FIG. 1 and FIG. 2 mayalso be used to illustrate the example operations. But the describedmethods are not limited to implementations on computing platform 100 orto graphics subsystem QoS manager 114. Also, logic and/or features ofgraphics subsystem QoS manager 114 may build or populate tablesincluding various power management and/or performance QoS values asshown in FIGS. 4-7. However, the example operations may also beimplemented using other types of tables to indicate current and targetQoS values.

Moving from the start to decision block 810 (Change of Mode?), graphicssubsystem QoS manager 114 may include logic and/or features configuredto determine whether a change in mode has occurred (e.g., via modefeature 211). In some examples, a change in mode may be responsive to achange in a type of usage of at least portions of computing platform100, an application request, a user request, an expiration of a timeinterval or an initialization of computing platform 100. If a change ofmode has occurred, the process moves to block 820. Otherwise, theprocess moves to block 890.

Moving from decision block 810 to block 820 (Receive Current PowerManagement and Performance QoS Values), graphics subsystem QoS manager114 may include logic and/or features configured to receive currentpower management and performance QoS values (e.g., via receive feature213). In some examples, the current power management and performance QoSvalues may be associated with a current type of usage for computingplatform 100 (e.g., web browsing). For these examples, graphicssubsystem QoS manager 114 may also include logic and/or features tobuild or populate tables (e.g., via current feature 215) based on thereceived current power management and performance QoS values. The tablesmay be similar in format to the tables 400 and 500 shown in FIGS. 4 and5 and described above.

Proceeding from block 820 to block 830 (Determine Current QM), graphicssubsystem QoS manager 114 may include logic and/or features configuredto determine a current QM (e.g., via current feature 215). In someexamples, the current QM may be determined based on the current powermanagement and performance QoS values. As described above for FIGS. 4and 5, in some examples, the current QM may be a combination of theaveraged power management and performance QoS values.

Proceeding from block 830 to block 840 (Receive Target Power Managementand Performance QoS Values), graphics subsystem QoS manager 114 mayinclude logic and/or features configured to receive target powermanagement and performance QoS values (e.g., via receive feature 213).In some examples, the target power management and performance QoS valuesmay be associated with a different or new type of usage for computingplatform 100 (e.g., interactive gaming). For these examples, graphicssubsystem QoS manager 114 may also include logic and/or features tobuild or populate tables (e.g., via target feature 215) based on thereceived target power management and performance QoS values. The tablesmay be similar in format to tables 600 and 700 shown in FIGS. 6 and 7and described above.

Proceeding from block 840 to block 850 (Determine Target QM), graphicssubsystem QoS manager 114 may include logic and/or features configuredto determine a target QM (e.g., via target feature 215). In someexamples, the target QM may be determined based on the target powermanagement and performance QoS values. As described above for FIGS. 6and 7, in some examples, the target QM may be a combination of theaveraged power management and performance QoS values.

Proceeding from block 850 to block 860 (Compare Current QM to TargetQM), graphics subsystem QoS manager 114 may include logic and/orfeatures configured to compare the current QM to the target QM (e.g.,via adjust feature 219).

Proceeding from block 860 to decision block 870 (Adjust?), graphicssubsystem QoS manager 114 may include logic and/or features configureddetermine whether one or more power management or performance attributesfor the one or more graphics subsystems of computing platform 100 needsto be adjusted (e.g., via adjust feature 219). In some examples,adjustments may be based on whether the current QM and the target QMmatch. If the current QM and the target QM do not at least approximatelymatch, the process moves to block 880. Otherwise, the process moves todecision block 890.

Moving from decision block 870 to block 880 (Adjust Power Management orPerformance Attributes), graphics subsystem QoS manager 114 may includelogic and/or features configured to adjust one or more power managementor performance attributes (e.g., via adjust feature 219) based on thecurrent QM and the target QM not matching. In some examples, the currentpower management or performance attributes may be changed such that theaverages of the average ratings for the power management and performanceattributes will change the current QM to at least approximately matchthe target QM.

In some other examples, an idle time-out window for one or more of thegraphics subsystems of computing platform 100 may be another powermanagement or performance attribute that is adjusted. For theseexamples, computing platform 100 may have limitations or constraintsthat make it difficult to adjust the power management or performanceattributes mentioned above for tables 400 and 500 to cause the currentQM to at least approximately match the target QM. The idle time-outwindow may be adjusted to a shorter time period to boost a powermanagement QoS value and lower a performance QoS value. Alternatively,the idle time-out window may be lengthened to lower the power managementQoS value and boost the performance power management QoS value.

Moving from block 880 to decision block 890 (Power Down?), graphicssubsystem QoS manager 114 may include logic and/or features configuredto determine whether computing platform 100 is powering down (e.g., viacurrent feature 215). If computing platform 100 is powering down theprocess comes to an end. Otherwise, the process moves back to decisionblock 810.

FIG. 9 illustrates an example system 900. In some examples, system 900may be a media system although system 900 is not limited to thiscontext. For example, system 900 may be incorporated into a personalcomputer (PC), laptop computer, ultra-mobile computer, tablet, touchpad, portable computer, handheld computer, palmtop computer, personaldigital assistant (PDA), cellular telephone, combination cellulartelephone/PDA, television, smart device (e.g., smart phone, smart tabletor smart television), mobile internet device (MID), messaging device,data communication device, and so forth.

According to some examples, system 900 includes a platform 902 coupledto a display 920. Platform 902 may receive content from a content devicesuch as content services device(s) 930 or content delivery device(s) 940or other similar content sources. A navigation controller 950 includingone or more navigation features may be used to interact with, forexample, platform 902 and/or display 920. Each of these components isdescribed in more detail below.

In some examples, platform 902 may include any combination of a chipset905, processor 910, memory 912, storage 914, graphics subsystem 915,applications 916 and/or radio 918. Chipset 905 may provideintercommunication among processor 910, memory 912, storage 914,graphics subsystem 915, applications 916 and/or radio 918. For example,chipset 905 may include a storage adapter (not depicted) capable ofproviding intercommunication with storage 914.

Processor 910 may be implemented as Complex Instruction Set Computer(CISC) or Reduced Instruction Set Computer (RISC) processors, x86instruction set compatible processors, multi-core, or any othermicroprocessor or central processing unit (CPU). In some examples,processor 910 may comprise dual-core processor(s), dual-core mobileprocessor(s), and so forth.

Memory 912 may be implemented as a volatile memory device such as, butnot limited to, a RAM, DRAM, or SRAM.

Storage 914 may be implemented as a non-volatile storage device such as,but not limited to, a magnetic disk drive, optical disk drive, tapedrive, an internal storage device, an attached storage device, flashmemory, battery backed-up SDRAM (synchronous DRAM), and/or a networkaccessible storage device. In some examples, storage 914 may includetechnology to increase the storage performance enhanced protection forvaluable digital media when multiple hard drives are included, forexample.

Graphics subsystem 915 may perform processing of images such as still orvideo for display. Similar to the graphics subsystems described abovefor FIG. 1, graphics subsystem 915 may include a processor serving as agraphics processing unit (GPU) or a visual processing unit (VPU), forexample. An analog or digital interface may be used to communicativelycouple graphics subsystem 915 and display 920. For example, theinterface may be any of a High-Definition Multimedia Interface,DisplayPort, wireless HDMI, and/or wireless HD compliant techniques. Forsome examples, graphics subsystem 915 could be integrated into processor910 or chipset 905. Graphics subsystem 915 could also be a stand-alonecard (e.g., a discrete graphics subsystem) communicatively coupled tochipset 905.

The graphics and/or video processing techniques described herein may beimplemented in various hardware architectures. For example, graphicsand/or video functionality may be integrated within a chipset.Alternatively, a discrete graphics and/or video processor may be used.As still another example, the graphics and/or video functions may beimplemented by a general purpose processor, including a multi-coreprocessor. In a further example, the functions may be implemented in aconsumer electronics device.

Radio 918 may include one or more radios capable of transmitting andreceiving signals using various suitable wireless communicationstechniques. Such techniques may involve communications across one ormore wireless networks. Example wireless networks include (but are notlimited to) wireless local area networks (WLANs), wireless personal areanetworks (WPANs), wireless metropolitan area network (WMANs), cellularnetworks, and satellite networks. In communicating across such networks,radio 918 may operate in accordance with one or more applicablestandards in any version.

In some examples, display 920 may comprise any television type monitoror display. Display 920 may include, for example, a computer displayscreen, touch screen display, video monitor, television-like device,and/or a television. Display 920 may be digital and/or analog. For someexamples, display 920 may be a holographic display. Also, display 920may be a transparent surface that may receive a visual projection. Suchprojections may convey various forms of information, images, and/orobjects. For example, such projections may be a visual overlay for amobile augmented reality (MAR) application. Under the control of one ormore software applications 916, platform 902 may display user interface922 on display 920.

According to some examples, content services device(s) 930 may be hostedby any national, international and/or independent service and thusaccessible to platform 902 via the Internet, for example. Contentservices device(s) 930 may be coupled to platform 902 and/or to display920. Platform 902 and/or content services device(s) 930 may be coupledto a network 960 to communicate (e.g., send and/or receive) mediainformation to and from network 960. Content delivery device(s) 940 alsomay be coupled to platform 902 and/or to display 920.

In some examples, content services device(s) 930 may comprise a cabletelevision box, personal computer, network, telephone, Internet enableddevices or appliance capable of delivering digital information and/orcontent, and any other similar device capable of unidirectionally orbidirectionally communicating content between content providers andplatform 902 and/display 920, via network 960 or directly. It will beappreciated that the content may be communicated unidirectionally and/orbidirectionally to and from any one of the components in system 900 anda content provider via network 960. Examples of content may include anymedia information including, for example, video, music, medical andgaming information, and so forth.

Content services device(s) 930 receives content such as cable televisionprogramming including media information, digital information, and/orother content. Examples of content providers may include any cable orsatellite television or radio or Internet content providers. Theprovided examples are not meant to limit the scope of this disclosure.

In some examples, platform 902 may receive control signals fromnavigation controller 950 having one or more navigation features. Thenavigation features of controller 950 may be used to interact with userinterface 922, for example. According to some examples, navigationcontroller 950 may be a pointing device that may be a computer hardwarecomponent (specifically human interface device) that allows a user toinput spatial (e.g., continuous and multi-dimensional) data into acomputer. Many systems such as graphical user interfaces (GUI), andtelevisions and monitors allow the user to control and provide data tothe computer or television using physical gestures.

Movements of the navigation features of controller 950 may be echoed ona display (e.g., display 920) by movements of a pointer, cursor, focusring, or other visual indicators displayed on the display. For example,under the control of software applications 916, the navigation featureslocated on navigation controller 950 may be mapped to virtual navigationfeatures displayed on user interface 922, for example. In some examples,controller 950 may not be a separate component but integrated intoplatform 902 and/or display 920. Although this disclosure is not limitedto the elements or in the context shown for controller 950.

According to some examples, drivers (not shown) may comprise technologyto enable users to instantly turn on and off platform 902 like atelevision with the touch of a button after initial boot-up, whenenabled. Program logic may allow platform 902 to stream content to mediaadaptors or other content services device(s) 930 or content deliverydevice(s) 940 when the platform is turned “off.” In addition, chip set905 may include hardware and/or software support for 5.1 surround soundaudio and/or high definition 7.1 surround sound audio, for example.Drivers may include a graphics driver for integrated graphics platforms.For some examples, the graphics driver may comprise a peripheralcomponent interconnect (PCI) Express graphics card.

In various examples, any one or more of the components shown in system900 may be integrated. For example, platform 902 and content servicesdevice(s) 930 may be integrated, or platform 902 and content deliverydevice(s) 940 may be integrated, or platform 902, content servicesdevice(s) 930, and content delivery device(s) 940 may be integrated, forexample. In various examples, platform 902 and display 920 may be anintegrated unit. Display 920 and content service device(s) 930 may beintegrated, or display 920 and content delivery device(s) 940 may beintegrated, for example. These examples are not meant to limit thisdisclosure.

In various examples, system 900 may be implemented as a wireless system,a wired system, or a combination of both. When implemented as a wirelesssystem, system 900 may include components and interfaces suitable forcommunicating over a wireless shared media, such as one or moreantennas, transmitters, receivers, transceivers, amplifiers, filters,control logic, and so forth. An example of wireless shared media mayinclude portions of a wireless spectrum, such as the RF spectrum and soforth. When implemented as a wired system, system 900 may includecomponents and interfaces suitable for communicating over wiredcommunications media, such as input/output (I/O) adapters, physicalconnectors to connect the I/O adapter with a corresponding wiredcommunications medium, a network interface card (MC), disc controller,video controller, audio controller, and so forth. Examples of wiredcommunications media may include a wire, cable, metal leads, printedcircuit board (PCB), backplane, switch fabric, semiconductor material,twisted-pair wire, co-axial cable, fiber optics, and so forth.

Platform 902 may establish one or more logical or physical channels tocommunicate information. The information may include media informationand control information. Media information may refer to any datarepresenting content meant for a user. Examples of content may includedata from a voice conversation, videoconference, streaming video,electronic mail (“email”) message, voice mail message, alphanumericsymbols, graphics, image, video, text and so forth. Data from a voiceconversation may be, for example, speech information, silence periods,background noise, comfort noise, tones and so forth. Control informationmay refer to any data representing commands, instructions or controlwords meant for an automated system. For example, control informationmay be used to route media information through a system, or instruct anode to process the media information in a predetermined manner. Theexamples mentioned above, however, are not limited to the elements or inthe context shown or described in FIG. 9.

FIG. 10 illustrates an example device 1000. As described above, system900 may be embodied in varying physical styles or form factors. FIG. 10illustrates examples of a small form factor device 1000 in which system900 may be embodied. In some examples, device 1000 may be implemented asa mobile computing device having wireless capabilities. A mobilecomputing device may refer to any device having a processing system anda mobile power source or supply, such as one or more batteries, forexample.

As described above, examples of a mobile computing device may include apersonal computer (PC), laptop computer, ultra-mobile computer, tablet,touch pad, portable computer, handheld computer, palmtop computer,personal digital assistant (PDA), cellular telephone, combinationcellular telephone/PDA, television, smart device (e.g., smart phone,smart tablet or smart television), mobile interne device (MID),messaging device, data communication device, and so forth.

Examples of a mobile computing device also may include computers thatare arranged to be worn by a person, such as a wrist computer, fingercomputer, ring computer, eyeglass computer, belt-clip computer, arm-bandcomputer, shoe computers, clothing computers, and other wearablecomputers. According to some examples, a mobile computing device may beimplemented as a smart phone capable of executing computer applications,as well as voice communications and/or data communications. Althoughsome examples may be described with a mobile computing deviceimplemented as a smart phone by way of example, it may be appreciatedthat other examples may be implemented using other wireless mobilecomputing devices as well. The examples are not limited in this context.

As shown in FIG. 10, device 1000 may include a housing 1002, a display1004, an input/output (I/O) device 1006, and an antenna 1008. Device1000 also may include navigation features 1012. Display 1004 may includeany suitable display unit for displaying information appropriate for amobile computing device. I/O device 1006 may include any suitable I/Odevice for entering information into a mobile computing device. Examplesfor I/O device 1006 may include an alphanumeric keyboard, a numerickeypad, a touch pad, input keys, buttons, switches, rocker switches,microphones, speakers, voice recognition device and software, and soforth. Information also may be entered into device 1000 by way ofmicrophone. For some examples, a voice recognition device may digitizesuch information. Although the disclosure is not limited in thiscontext.

Various examples may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an example isimplemented using hardware elements and/or software elements may vary inaccordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one example may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor.

Various examples may be implemented using hardware elements, softwareelements, or a combination of both. In some examples, hardware elementsmay include devices, components, processors, microprocessors, circuits,circuit elements (e.g., transistors, resistors, capacitors, inductors,and so forth), integrated circuits, application specific integratedcircuits (ASIC), programmable logic devices (PLD), digital signalprocessors (DSP), field programmable gate array (FPGA), memory units,logic gates, registers, semiconductor device, chips, microchips, chipsets, and so forth. In some examples, software elements may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an example isimplemented using hardware elements and/or software elements may vary inaccordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

Some examples may include an article of manufacture. An article ofmanufacture may include a non-transitory storage medium to store logic.In some examples, the non-transitory storage medium may include one ormore types of computer-readable storage media capable of storingelectronic data, including volatile memory or non-volatile memory,removable or non-removable memory, erasable or non-erasable memory,writeable or re-writeable memory, and so forth. In some examples, thelogic may include various software elements, such as softwarecomponents, programs, applications, computer programs, applicationprograms, system programs, machine programs, operating system software,middleware, firmware, software modules, routines, subroutines,functions, methods, procedures, software interfaces, application programinterfaces (API), instruction sets, computing code, computer code, codesegments, computer code segments, words, values, symbols, or anycombination thereof.

According to some examples, an article of manufacture may include anon-transitory storage medium to store or maintain instructions thatwhen executed by a computer or system, cause the computer or system toperform methods and/or operations in accordance with the describedexamples. The instructions may include any suitable type of code, suchas source code, compiled code, interpreted code, executable code, staticcode, dynamic code, and the like. The instructions may be implementedaccording to a predefined computer language, manner or syntax, forinstructing a computer to perform a certain function. The instructionsmay be implemented using any suitable high-level, low-level,object-oriented, visual, compiled and/or interpreted programminglanguage.

Some examples may be described using the expression “in one example” or“an example” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one example. The appearances ofthe phrase “in one example” in various places in the specification arenot necessarily all referring to the same example.

Some examples may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example,descriptions using the terms “connected” and/or “coupled” may indicatethat two or more elements are in direct physical or electrical contactwith each other. The term “coupled,” however, may also mean that two ormore elements are not in direct contact with each other, but yet stillco-operate or interact with each other.

It is emphasized that the Abstract of the Disclosure is provided tocomply with 37 C.F.R. Section 1.72(b), requiring an abstract that willallow the reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single example for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimed examplesrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter lies in lessthan all features of a single disclosed example. Thus the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate example. In the appended claims,the terms “including” and “in which” are used as the plain-Englishequivalents of the respective terms “comprising” and “wherein,”respectively. Moreover, the terms “first,” “second,” “third,” and soforth, are used merely as labels, and are not intended to imposenumerical requirements on their objects.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A method comprising: receiving, by a processorcircuit, a current power management quality of service (QoS) value and acurrent performance QoS value, the current power management andperformance QoS values associated with a first mode of operation;determining a current quality metric based on the current powermanagement and performance QoS values; receiving, by the processorcircuit, a target power management QoS value and a target performanceQoS value, the target power management and performance QoS valuesassociated with a second mode of operation; determining a target qualitymetric based on the target power management and performance QoS values;and adjusting one or more power management or performance attributes forone or more graphics subsystems of a computing platform based on acomparison of the current quality metric to the target quality metric.2. The method of claim 1, comprising adjusting the one or more powermanagement or performance attributes by adjusting an idle time-outwindow, the idle time-out window to include a time interval for whichthe one or more graphics subsystems remain in an active state followingexecution of a command before transitioning into a low power state. 3.The method of claim 1, comprising both the target power management andperformance QoS values and the current power management and performanceQoS values being received based on a change of mode of operation fromthe first mode of operation to the second mode of operation.
 4. Themethod of claim 3, comprising the change of mode of operation beingresponsive to one of a change in a type of usage of the one or moregraphics subsystems, an application request, a user request, anexpiration of a time interval or an initialization of the computingplatform.
 5. The method of claim 4, comprising the type of usageincluding one of web browsing, video playback, interactive game, imagecapture or default.
 6. The method of claim 4, comprising the applicationrequest or the user request including information associated with thereceived target power management and performance QoS values.
 7. Themethod of claim 1, comprising the target and current power managementQoS values including at least one of a display attribute, a graphics andvideo attribute or a system attribute.
 8. The method of claim 7,comprising the display attribute including at least one of a resolution,a brightness, a refresh rate or a pixel size depth, the graphics andvideo attribute including at least one of a compressed texture format, arender target, a type of overlay for rendering, a frequency for one ormore graphics subsystems to execute, a copy rate from source buffer to adestination buffer, a mipmap or a video compression ratio and, thesystem attribute including at least one of a system state for thecomputing platform and a battery life for the computing platform.
 9. Themethod of claim 1, comprising the target and current performance QoSvalues including at least one of a display attribute, a graphicsattribute, a video attribute, an application attribute or a userexperience attribute.
 10. The method of claim 9, comprising the displayattribute including at least one of a resolution, a brightness, arefresh rate or a pixel size depth, the graphics attribute including atleast one of a compressed texture format, a render target, a type ofoverlay for rendering, a frequency for one or more graphics subsystemsto execute, a copy rate from source buffer to a destination buffer or amipmap, the video attribute includes a compression ratio, theapplication attribute including a maximum latency tolerance and, theuser experience attribute including a maximum response time.
 11. Themethod of claim 1, comprising both the target and the current qualitymetrics including averaged target power management and performance QoSvalues, and adjusting one or more power management or performanceattributes includes adjusting the one or power management or performanceattributes such that adjusted current power management and performanceQoS values approximately match the averaged target power management andperformance scores.
 12. An apparatus comprising: a processor circuit;and a memory unit communicatively coupled to the processor circuit, thememory unit arranged to store a graphics subsystem quality of service(QoS) manager operative on the processor circuit to determine a currentquality metric based on current power management and performance QoSvalues associated with a first mode of operation, determine a targetquality metric based on target power management and performance QoSvalues associated with a second mode of operation, and adjust one ormore power management or performance attributes for one or more graphicssubsystems for a computing platform based on a comparison of the currentquality metric to the target quality metric.
 13. The apparatus of claim12, comprising the memory unit arranged to store an operating system forthe computing platform, the operating system operative on the processorcircuit to provide platform power management, the platform powermanagement configured to provide one or more current power managementQoS values to the graphics subsystem QoS manager.
 14. The apparatus ofclaim 12, comprising the memory unit arranged to store an operatingsystem for the computing platform, the operating system operative on theprocessor circuit to provide a device driver, the device driverconfigured to provide one or more current performance QoS values to thegraphics subsystem QoS manager.
 15. The apparatus of claim 12,comprising the graphics subsystem quality of service QoS manager tocause an adjustment to an idle time-out window to adjust the one or morepower management or performance attributes, the idle time-out window toinclude a time interval for which the one or more graphics subsystemsare to remain in an active state following execution of a command beforetransitioning into a low power state.
 16. The apparatus of claim 12,comprising the graphics subsystem quality of service QoS manager toreceive the target power management and performance QoS values based ona change of mode of operation from the first mode of operation to thesecond mode of operation.
 17. The apparatus of claim 16, comprising thechange of mode of operation responsive to one of a change in a type ofusage of the one or more graphics subsystems, an application request, auser request, an expiration of a time interval or an initialization ofthe computing platform.
 18. The apparatus of claim 17, comprising theapplication request or the user request including information associatedwith the target power management and performance QoS values.
 19. Theapparatus of claim 12, comprising the target and current powermanagement QoS values including at least one of a display attribute, agraphics and video attribute or a system attribute.
 20. The apparatus ofclaim 12, comprising the target and current performance QoS valuesincluding at least one of a display attribute, a graphics attribute, avideo attribute, an application attribute or a user experienceattribute.
 21. The apparatus of claim 12, comprising both the target andthe current quality metrics including averaged target power managementand performance QoS values, the graphics subsystem quality of serviceQoS manager to adjust one or more power management or performance suchthat adjusted current power management and performance QoS valuesapproximately match the averaged target power management and performancescores.
 22. The apparatus of claim 12, comprising a digital display, thegraphics subsystem QoS manager configured to adjust one or more powermanagement or performance attributes for graphics and video to bedisplayed on the digital display based on the comparison of the currentquality metric to the target quality metric.
 23. An article ofmanufacture comprising a storage medium containing instructions thatwhen executed cause a system to: receive a current power managementquality of service (QoS) value and a current performance QoS value, thecurrent power management and performance QoS values associated with afirst mode of operation and one or more graphics subsystems for acomputing platform; determine a current quality metric based on thecurrent power management and performance QoS values; receive a targetpower management QoS value and a target performance QoS value, thetarget power management and performance QoS values associated with asecond mode of operation and the one or more graphics subsystems;determine a target quality metric based on the target power managementand performance QoS values; and adjust one or more power management orperformance attributes for the one or more graphics subsystems based ona comparison of the current quality metric to the target quality metric.24. The article of manufacture of claim 23, comprising the instructionsto cause the system to cause an adjustment to an idle time-out window toadjust one or more power management or performance attributes, the idletime-out window to include a time interval for which the one or moregraphics subsystems remain in an active state following execution of acommand before transitioning into a low power state.
 25. The article ofmanufacture of claim 24, comprising the target power management andperformance QoS values received based on a change of mode of operationfrom the first mode of operation to the second mode of operation. 26.The article of manufacture of claim 25, comprising the change of mode ofoperation responsive to one of a change in a type of usage of the one ormore graphics subsystem, an application request, a user request, anexpiration of a time interval or an initialization of the computingplatform.
 27. The article of manufacture of claim 26, comprising theapplication request or the user request including information associatedwith the target power management and performance QoS values.
 28. Thearticle of manufacture of claim 23, comprising both the target and thecurrent quality metrics to include averaged target power management andperformance QoS values, and to adjust one or more power management orperformance attributes includes adjusting the one or power management orperformance attributes such that adjusted current power management andperformance QoS values approximately match the averaged target powermanagement and performance scores.